meta: bump the next-js group across 1 directory with 4 updates#117
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
meta: bump the next-js group across 1 directory with 4 updates#117dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps the next-js group with 4 updates in the / directory: [@vercel/analytics](https://github.com/vercel/analytics/tree/HEAD/packages/web), [@vercel/speed-insights](https://github.com/vercel/speed-insights/tree/HEAD/packages/web), [next](https://github.com/vercel/next.js) and [turbo](https://github.com/vercel/turbo). Updates `@vercel/analytics` from 1.2.2 to 1.3.1 - [Release notes](https://github.com/vercel/analytics/releases) - [Commits](https://github.com/vercel/analytics/commits/1.3.1/packages/web) Updates `@vercel/speed-insights` from 1.0.10 to 1.0.12 - [Release notes](https://github.com/vercel/speed-insights/releases) - [Commits](https://github.com/vercel/speed-insights/commits/1.0.12/packages/web) Updates `next` from 14.2.3 to 14.2.5 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.3...v14.2.5) Updates `turbo` from 1.13.3 to 2.0.11 - [Release notes](https://github.com/vercel/turbo/releases) - [Changelog](https://github.com/vercel/turbo/blob/main/release.md) - [Commits](vercel/turborepo@v1.13.3...v2.0.11) --- updated-dependencies: - dependency-name: "@vercel/analytics" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: next-js - dependency-name: "@vercel/speed-insights" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: next-js - dependency-name: next dependency-type: direct:production update-type: version-update:semver-patch dependency-group: next-js - dependency-name: turbo dependency-type: direct:development update-type: version-update:semver-major dependency-group: next-js ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
removed
the
github_actions:pull-request
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the next-js group with 4 updates in the / directory: @vercel/analytics, @vercel/speed-insights, next and turbo.
Updates
@vercel/analyticsfrom 1.2.2 to 1.3.1Release notes
Sourced from
@vercel/analytics's releases.Commits
cc5a474fix: nextjs parallel routes with catchall isn't supported (#141)74942cd[web] Include flags in custom events (#140)Updates
@vercel/speed-insightsfrom 1.0.10 to 1.0.12Release notes
Sourced from
@vercel/speed-insights's releases.Commits
5e6ff8cfix(#56,#72): useSearchParams might return null and break script insertion (#73)fe76ed0fix(#68): postinstall is failing with no error68d3424fix: nextjs parallel routes with catchall isn't supported (#69)Updates
nextfrom 14.2.3 to 14.2.5Release notes
Sourced from next's releases.
Commits
0bf7f52v14.2.530d6dfcfix: metadata route merging conflicts186ec6bLog stdio for pull-turbo-cache script (#66759)45656d3Ensure turbo is setup when building in docker (#66804)08e7fd1Upgrade acorn (#67592)1d08dabavoid merging global css in a way that leaks into other chunk groups (#67373)21a9d59Fix server action edge redirect with middleware rewrite (#67148)1b10b13fix(next): reject protocol-relative URLs in image optimization (#65752)c64c61dfix(next-swc): correct path interop to filepath for wasm (#65633)6c661d2Use addDependency to track metadata route file changes (#66714)Updates
turbofrom 1.13.3 to 2.0.11Release notes
Sourced from turbo's releases.
... (truncated)
Commits
078f4b2publish 2.0.11 to registryc90d33cfix(pty): disable echoctl for child processes (#8892)56277b0smarter logical combination that keeps truthy/falsy/nullish property (#8873)49c6759Convert MDX errors into issues (#8879)727d5e0Make JS Lints have lower severity (#8837)d3db2f5fix(ci): Trying to fixbenchmark-turbopackworkflow (#8090)75870c6(docs): Mention sideEffects key in Internal Packages documentation. (#8888)adcf0f7release(turborepo): 2.0.10 (#8886)e27857dfix(windows): keep stdin open for conpty processes (#8885)68bbb1fadds daemon flag for env var and turbo.json (#8728)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions